home *** CD-ROM | disk | FTP | other *** search
- Path: news.eunet.fi!newsmaster
- From: bjb@esmiodt.esmi.ahlstrom.com
- Newsgroups: alt.winsock,comp.lang.c++,comp.os.ms-windows.networking.tcp-ip,alt.winsock.programming
- Subject: Re: Why is Novell TCP/IP not working?
- Date: 12 Jan 1996 07:22:42 GMT
- Organization: Oy Esmi Ab, Finland
- Distribution: world
- Message-ID: <4d5282$pvk@idefix.eunet.fi>
- References: <TERRY.11.00295CF0@CAM.ORG>
- NNTP-Posting-Host: bjb.esmi.ahlstrom.com
- X-Newsreader: News for Windows NT X1.0-43
-
- In article <TERRY.11.00295CF0@CAM.ORG>
- TERRY@CAM.ORG (Terry Drymonacos) wrote:
-
- > Hi
- >
- > I wonder if anyone out there has experienced this phenomenon with their Novell
- > Lan WorkPlace Windows Sockets API v1.1?
- >
- > I'm trying to write a server application, I'm able to intitiate a
- > WSAStartup(), make a socket, bind it but as soon as I call WSAAsynchSelect() I
- > get a ENETDOWN error. I've tried using a utility called Windows Socket Test
- > and it gives me the same result. I have tried the same program and Socket test
- > program on my solitary computer at home using Trumpet winsock and everything
- > is fine, which leads me to conclude that Novell may be the culprit.
- >....
-
- I wonder if this problem is related to a same sort of problem we had with our
- winsock-based program. After starting to use WSAAsyncSelect we heard from some
- of our customers using Novell TCP/IP that the client doesn't work. After examining
- their configuration I found out that if the program NOVASYNC.EXE is not found in the
- program path, our winsock program will not work. After adding the appropriate
- NOVASYNC.EXE to the network program directory everything works fine.
- Don't ask me what NOVASYNC.EXE does but it solved our problems. (NOVASYNC.EXE
- do belong to the Novell TCP/IP client package).
-
- Bengt Bredenberg
- bjb@esmiodt.esmi.ahlstrom.com
-
-
-